Release Notes
October 2020
What's New
Our October release is all about improved performance. Though not visible in the product user interface, there are several back-end improvements going live, which include:
Shorter Maintenance Windows - We’ve upgraded our deployment process to ensure shorter maintenance windows during product upgrades.
Background Location Access Permission
- Admins can now control the background location access permission for apps in Android 10+.
iOS Commands - Admins can now send an unenroll or wakeup command to an iOS device in an unenrolling state—additional functionality that gives an admin more active control.
Help Center Videos
- Our video library has been split into smaller sections by category to make finding what you need easier. The revised video section also includes a table of contents for faster navigation.
Resolved Issues
Bug fixes are included in the resolved issues list for two release periods and are then retired.
| Issue |
Description |
Status |
| 4569 - Deleting a VPN configuration from a Windows 10 device was not completely removing it. |
Delete command will now completely delete a VPN on Windows 10 device.
|
FIXED
|
| 4567 - The Find My Mac PIN is not recorded in the database and not displayed in the admin portal after a factory reset command is sent to a macOS device. |
Find My Mac PIN is recorded in the database and in shown the device details section of the admin portal.
|
FIXED
|
| 4562 - Deleting a user with a device in a "Discovered" status assigned to them resulted in the DEP device being set to "Unenrolled" instead of "Discovered". |
DEP devices stay discovered after associated user is deleted.
|
FIXED
|
| 4558 - "Clear Restrictions" command/menu item |
The "Clear Restrictions" command has been removed in favor of selecting and removing the restriction sets directly from the "Restriction Sets" tab of the device detail screen.
|
FIXED
|
| 4545 - The "applies to" device count in the command confirmation dialog would sometimes show an incorrect number. |
When issuing a "Check for OS Update" command to multiple devices, the applicable/inapplicable device count correctly adds up to the number of selected devices.
|
FIXED
|
| 4542 - If a user account was deleted and recreated using the same email address, the system would not properly get and set settings for the user, resulting in behaviors such as the maintenance window reminders not showing up properly. |
User can log in successfully and the network trace shows a success for the call to GET UserSettings
|
FIXED
|
| 4538 - The "SAML Federation Metadata Document URL" field was not a required field. |
URL field is now required.
|
FIXED
|
| 4534 - When editing a restriction set, searching for the block/allow list restriction would result in the restriction not being editable without first clearing the search and locating the restriction in the list. |
User can now filter the restrictions list by the keyword "app" and add/remove apps from the block/allow list.
|
FIXED
|
| 4533 - The unlock command is sent to all/some users instead of the one being selected. |
Single unlock command sent to device for selected user.
|
FIXED
|
| 4532 - Linking a vendor profile to a policy would also link previously deleted profiles to the policy. |
Admin can select all vendor profiles in policies/vendor profiles and link/unlink without other profiles being linked or unlinked.
|
FIXED
|
| 4527 - With the release of web authentication support for DEP enrollment last month, we have reduced the visibility of the "Generate Token" button during the enrollment process since it is only needed for older Mac devices. |
Cleaner enrollment experience for macOS.
|
FIXED
|
| 4521 - If a PFX or PKSC certificate was previously deployed and then deleted from a Windows 10 device, reinstalling it fails. |
Device history shows the command completed successfully and a subsequent device inventory should verify that the certificate is installed on the device.
|
FIXED
|
| 4516 - Android 10+: Admin cannot control ‘deny’ or ‘permanently grant’ access for apps requiring background location access. |
Admins can allow or disallow background location access for an app on Android 10+.
|
FIXED
|
| 4346 - Unable to Login to macOS 11.0 Device After Adding FileVault Profile.
|
After applying a FileVault profile to a macOS 11.0 device, the device user can now log inon both virtual and physical devices.
|
FIXED
|
| 4311 - Cert upload uses "undefined" string as password if none is specified. |
.p12 or pfx certificates with a blank password get uploaded with a password of "undefined" instead of being left empty.
|
FIXED
|
| 4265 - Double-clicking the "Create New User" button on the Edit User screen results in a "User already exists" error. |
Save button is now disabled after a single click.
|
FIXED
|
| 4031 - App list when importing to device does not show app configs
|
The list of apps available for adding includes one item for every App + App Config combination. |
FIXED
|
| 3568 - Send commands to "Unenrolling" device |
Admins can now send an unenroll command to a device in an unenrolling state, as well as send a wakeup command to an iOS device in an unenrolling state. |
FIXED
|
Known Issues
| Issue |
Description |
Status |
| 3514 - iOS update command does not display status feedback. |
iOS command to update OS uses default action that will typically download but not install. Fix to display status feedback. |
Open
|
| 3286 - Apparent mismatch between device compliance and individual entity compliance. |
Occasionally the policy details for a device may show success even if the entity in question did not successfully install.
|
Open
|
| Role Management and SSO Configuration
|
If user role assignment is set to Automatic during SSO Configuration, a manual attempt to update an individual user's role via the Users > Edit User path may appear possible, but will be overwritten by the original SSO Configuration. To resolve, the configuration setting can be changed to Manual, which will then enable editing of individual user roles. |
Open
|
| Android - Restrictions |
Restrictions that are configured to deploy upon enrollment may not immediately appear in the inventory for impacted devices; however, the restrictions will be enforced on the device.
|
Open
|
| Android - Device Owner Setup
|
When using the Device Owner enrollment flow (afw#kace), the enrollment flow may not complete if the Google Play services on the factory default image of the device are out of date. This a known issue with the Android operating system, caused by the enrollment process timing out before the update of the Play Services on the device can complete. You will know that this situation occurred if you are never asked for your subdomain name during the enrollment process. If you end up back at the device home screen, locate and launch the KACE Cloud MDM agent app on the device and click the 'Enroll Device' button to complete the setup process.
|
Open
|
| Android - Gmail App
|
Android devices require the Gmail app to be installed in order to use the email account configurations.
|
Open
|
| Android - Set and Clear Passcode Commands
|
The set and clear passcode functions are different in Android 7.0 and later. On versions prior to 7.0, an administrator could set or clear the passcode as desired. On Android 7.0 and later, the passcode can only be set on devices that do not already have a passcode set, and passcodes cannot be cleared. The user interface does not currently warn users who are attempting to set or clear a passcode on Android 7.0 and later, but an error message will appear. Note that attempting to clear a passcode will also fail if there is a policy in place that requires use of a passcode to do so.
|
Open
|
| iOS - Factory Reset: Apple iOS iCloud Account Lock
|
When resetting an Apple iOS device back to factory defaults, the device will remain locked to the associated iCloud account. To prevent this from happening, before resetting the device, manually turn off the 'Find my phone' feature on the iPhone.
|
Open
|
Additional Resources
Getting Started with KACE Cloud MDM
© 2020 Quest Software Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.
The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.
If you have any questions regarding your potential use of this material, contact:
Quest Software Inc.
Attn: LEGAL Dept.
4 Polaris Way
Aliso Viejo, CA 92656
Refer to our website (www.quest.com) for regional and international office information.
Patents
Quest Software is proud of our advanced technology. Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at www.quest.com/legal.
Trademarks
Quest and the Quest logo are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at www.quest.com/legal. All other trademarks, servicemarks, registered trademarks, and registered servicemarks are the property of their respective owners.